chore: standardize robots.txt for SEO crawl budget optimization - #6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Standardized
robots.txtto optimize SEO crawl budget.Based on a Cloudflare bot traffic audit (30 days, 118M bot requests across decocdn.com + deco.site), we found that 40%+ of bot crawl budget is wasted on internal framework endpoints, backend APIs, filter explosion URLs, and tracking parameters.
Blocked
Deco framework:
/live/invoke— server function endpoint (returns empty JSON on GET)/api/,/no-cache/,/proxy/,/graphql/— backend API proxiesTracking params (duplicate content):
gclid,fbclid,srsltid, etc.)NOT blocked
/_frsh/js/*— needed for Google Web Rendering Service/deco/render— partial section renderer, needed for page rendering qualityReferences